|
|
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Star Striker
   |
Posted - 2010.06.14 05:50:00 -
[1]
Edited by: Star Striker on 14/06/2010 05:50:05
My PI Optimizer is aimed for people who want to quickly evaluate the best way to extract resources from a planet.
The tool shows you what kind of setups you can expect to run on a planet, while being as effective as possible, hauling stuff as seldom as possible.
To use this tool efficiently, it is assumed you already know quite a lot about PI. There are lots of tutorials on t3h internetz already about PI. An integrated guide about the linking and routing strategy is under way, however.
This is the very first beta - coded overnight  , so comments, feedback and suggestions are most welcome. Many ideas are already brewing.
Star Striker's P0 Planet Optimizer
|
Star Striker
|
Posted - 2010.06.14 13:05:00 -
[2]
Quetazal: Storage facilities will in deed be replaced by launch pads in a coming version. They just eat a lot of CPU. Thus, I'm bringing in CPU checking also, although that will not have a big part in the GUI.
The Huffarunier: Yes, more images to represent more accurately the current setup would surely be nice. Coming soon.
Jackomel: I have planned those features, yes. P3-P4 production/hauling planning for multiple planets (managing your saved planets) is something we'll see eventually...
Thanks very much for the initial feedback! Keep it coming! 
|
Star Striker
|
Posted - 2010.06.14 17:54:00 -
[3]
Version 0.4 is out. Major GUI overhaul, manual tweaking options, and moar.
|
Star Striker
|
Posted - 2010.06.14 21:38:00 -
[4]
ChrisIsherwood,
For the current version of the tool, the calculations do work as expected. The reason why you get the same amount of P2 processing power with both 800/cycle and 1400/cycle is this:
* The tool always opts for perfect P1 -> P2 processing ratio. This means there shall always be twice the number of P1 processors compared to P2 processors.
* The tool currently seeks more gladly for a P1 efficiency of less than 100. It currently trusts that users will likely forget resurveying their extractors every now and then.
I'm currently improving the intelligence of the suggest algorithm. It should work better in a few hours, when I'm releasing version 0.5, which also checks for CPU requirements, and fixes a major bug in the GUI. Stay tuned.
Thanks for pointing this out. 
|
Star Striker
|
Posted - 2010.06.15 00:35:00 -
[5]
v0.5 has been released.
* Heavy tweaking on P0/P1/P2 analyzing for the best results.
* P1 and P2 calculations take P0 extracting capability into account when P1 processing capability exceeds it.
* CPU checking support for mega-storage fans.
* Code rewriting and changes to support P3 production and refills from other planets in the future  (Not promising any time table)
|
Star Striker
|
Posted - 2010.06.15 12:59:00 -
[6]
Licinius CrassusFilius: Thanks for suggesting - you're not alone. Two parallel P0 cycle setups will be supported soon. 
The Huffarunier: Agreed, currently the tool always tries to match P1 processors to full P2 capacity. In your case, I agree, 3 P1 and 2 P2 processors would be a wiser setup. Thanks for pointing this out. I will improve the suggestion intelligence to support these types of scenarios.
Once our planetary skills replicate on Sisi, I will have much more time to emphasize also on high sec and low sec planets' typical P0 outputs.
Thanks for the feedback (and donations) again!
|
Star Striker
|
Posted - 2010.06.15 16:33:00 -
[7]
 Originally by: Profhet
Can you tell us in general what you used to do this? is it just javascript?
It uses server side processing, mostly. Technology is Adobe ColdFusion 9. I've been working with CF since 1997. Upcoming versions will also use MySQL database.
|
Star Striker
|
Posted - 2010.06.17 01:21:00 -
[8]
Version 0.6 has been released, with yet advanced setup suggestion intelligence.
Have fun
|
|
|
| |
|